home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ETO Development Tools 4
/
ETO Development Tools 4.iso
/
Tools - Objects
/
MacsBug
/
MacsBug 6.1
/
Read Me First
< prev
Wrap
Text File
|
1989-04-21
|
3KB
|
64 lines
Installing MacsBug:
Copy the files MacsBug and "Debugger Prefs" to the System folder on your
boot disk and reboot. The MacsBug file is required. The "Debugger Prefs"
file is optional. It contains macros, templates and other MacsBug resources
that are loaded if present.
Installing MacsBug to minimize RAM usage:
Copy the file MacsBug to the System folder on your boot disk. Use ResEdit
to remove the 'mxbh' resource (help text) from the MacsBug file that you just
copied. Make sure there is not a debugger prefs file in your System folder.
Reboot.
What the Resources folder contains:
This folder contains the following resources that can be pasted into the
Debugger Prefs file to increase MacsBug functionality.
Floating Point Macros to support A-Trap breaks at FP68K calls
HFS Calls Macros to support A-Trap breaks at HFSDispatch calls
List Manager Macros to support A-Trap breaks at Pack0 calls
C++ Code to unmangle C++ names
KCHR The key map to use for the MacsBug keyboard.
This is used to debug international software.
The folder "MPW .r files" contains the text that was used to create the
MacsBug resources. Macros.r, Templates.r, Init.r and Color.r are shipped
as resources in the Debugger Prefs file since they are commonly used.
FloatingPoint.r, HFSCalls.r and ListManager.r are shipped as separate
resources since they are not as widely used.
The Debugger Prefs file also contains TMPL resources used by ResEdit to edit
MacsBug resources. Earlier versions of ResEdit may require you to paste
them into ResEdit to use them.
What the dcmds folder contains:
This folder contains tools used to build and test dcmds, sample dcmds in both
C and Pascal and contributed dcmds.
The MPW tool BuildDcmd is used to convert a linked application into a dcmd and
installs it into the Debugger Prefs file.
The application TestDcmd simulates the environment in which a dcmd executes.
This allows you to use MacsBug while debugging a dcmd.
The Samples folders contain the source of dcmds written specifically to
demonstrate the various call back routines used by dcmds. The source is
provided in both C and Pascal. This folder also contains the dcmd interface
files (.h and .p respectively) and the glue file to be linked with your dcmd.
The Contributed dcmds folder contains dcmds that we find useful at Apple.
Information about each one is available in MacsBug by typing "HELP name". The
source for these commands is included. If you write an interesting dcmd and
would like to have it considered for future versions of MacsBug then contact
Michael Tibbott (AppleLink = TIBBOTT) or Tom Chavez (AppleLink = TOM.CHAVEZ).